-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix affected target computation breaking CI workflows when no targets are affected #2696
Fix affected target computation breaking CI workflows when no targets are affected #2696
Conversation
(Note that this is effectively in 'draft' mode but can't actually be marked as draft since we need to run CI for investigation here). |
While Bazel can run an empty list of tests, GitHub actions always expects at least 1 entry for matrix-dependent actions. This is based on https://github.community/t/empty-matrix-fails-workflow/128736/2. It's not yet clear if this will properly allow check_test_results to pass if the workflow is skipped. That will need to be tested.
https://github.community/t/empty-matrix-fails-workflow/128736/2 seems like a viable fix. |
Now that #2710 is merged restarting these workflows to see if I fixed the issue. |
…ithub.com:oppia/oppia-android into fix-incorrect-affected-target-handling-when-empty
Yay, looks like this solution works. However, it does cause the check test results action to fail. :( I was partly expecting that to happen. I guess we need to also need to condition the steps of that task or something. Need to think on it a bit more. |
Awesome, it's passing now. Reenabling other tests & sending this out for review. |
Reenable jobs.
Undo removing the newline since it's not actually needed.
I forgot that we're performing an empty check, so the extra newline does break it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks @BenHenning
See #2691 (comment) & https://github.com/oppia/oppia-android/actions/runs/560112155 for context. It seems when there are no affected targets an empty line will be printed which breaks something between the jobs. I think this will fix it.
Conveniently, this PR should trigger the "no affected targets" workflow & can self-verify itself.